Versions:

  • 1.18.0
  • 1.17.0
  • 1.16.0
  • 1.15.5
  • 1.15.4
  • 1.15.3
  • 1.15.2
  • 1.15.1
  • 1.15.0
  • 1.14.0
  • 1.13.1
  • 1.13.0
  • 1.12.0
  • 1.11.0
  • 1.10.0
  • 1.9.0
  • 1.8.0
  • 1.7.0
  • 1.6.0
  • 1.5.2
  • 1.4.0
  • 1.3.0
  • 1.0.0

ChangeRig is a software tool published by RigSmith, currently available at version 1.18.0 as part of a release history comprising 23 versions. The tool is positioned in the version management and release tooling category of the software catalog, addressing the challenges that development teams face when coordinating version changes across diverse technology environments. According to the publisher's description, ChangeRig is built around the concept of changesets: it enables users to capture intent first and then apply versioning across every ecosystem. This intent-first approach reflects the tool's stated purpose, which is to record the reasoning and scope behind a change before that change is propagated into versioned releases. The emphasis on spanning every ecosystem indicates that ChangeRig is intended for use cases where software projects do not live within a single language, package manager, or distribution channel, but instead need consistent versioning behavior across multiple such environments. Typical use cases, as implied by its description, include capturing the intent of modifications at the time they are made, organizing those modifications into changesets, and then using that captured information to drive version updates across the ecosystems in which a project participates. This makes the tool relevant for teams maintaining cross-ecosystem projects, polyglot repositories, or any development workflow where versioning decisions must remain coherent and traceable rather than being reconstructed after the fact. The current release, version 1.18.0, follows a 1.x release line and represents the eighteenth minor iteration within that major version series, suggesting an actively maintained product with an established release cadence. With 23 recorded versions in total, the catalog entry reflects a substantial history of updates, giving users multiple prior releases to reference when reviewing compatibility, planning upgrades, or pinning specific versions for their environments.

Tags: